Am 22.08.23 um 04:19 schrieb Benjamin Buchmuller:
I had the same question a couple of days ago and I found a thread on the
mailing list, which I'm reposting here. Although this worked for me, I found
downsampling of the pdf with gs more convenient.
Here’s a shorter solution:
\startluacode
Hi Julian,
I had the same question a couple of days ago and I found a thread on the
mailing list, which I'm reposting here. Although this worked for me, I found
downsampling of the pdf with gs more convenient.
Hope this helps,
Benjamin
%
if not modules then modules = { } end modules
Just wondering: in programs like InDesign, Viva Designer, it is trivial
to produce a low resolution pdf output (useful when exchanging a hi-res
file with authors and editors prior to pre-print is difficult). I assume
it might be possible to do so in ConTeXt. Currently I use a script (gs
Here's another math symbol that I think is too low: the vertical bar in
Palatino/Pagella. Here's an almost-minimal example. I've left in the
surrounding text, to show how it's used (in probability, as P(H|E)).
I think the bottom of the bar is correct, but the tip of the bar doesn't
reach
) of
the parentheses, while in Palatino (Pagella) this does not seem to be the case.
Best regards: OK
On 9 mai 2014, at 23:06, Sanjoy Mahajan san...@mit.edu wrote:
Here's another math symbol that I think is too low: the vertical bar in
Palatino/Pagella. Here's an almost-minimal example. I've left
On Wed, May 7, 2014 at 2:34 AM, Sanjoy Mahajan san...@mit.edu wrote:
the + aligns on the math axis so one can argue if the type-one variant
is ok ... so we would need a smaller (less height) + then which would
look visually weird
Plain TeX doesn't align the plus/minus to the math axis.
On 7 mai 2014, at 10:46, Mikael P. Sundqvist mic...@gmail.com wrote:
[…]
I guess one could do this for the other signs one don't like in TeX
Gyre Pagella Math…
Hi,
This is a good trick to know, especially if one combines \pm and \mp as in the
counter-example given by Hans:
% Start
Continuing my recent theme of finding glyphs too low or too high:
The \pm symbol looks like it is set too low, in MkIV.
\setuppagenumbering[location=]
\starttext
$\pm2$
\stoptext
The minus part of the sign lies below the baseline, which looks odd
relative to the horizontal stroke of the 2
On Tue, May 6, 2014 at 4:22 PM, Sanjoy Mahajan san...@mit.edu wrote:
Continuing my recent theme of finding glyphs too low or too high:
The \pm symbol looks like it is set too low, in MkIV.
\setuppagenumbering[location=]
\starttext
$\pm2$
\stoptext
The minus part of the sign lies below
the placement is due to the new LM Math font.
-Sanjoy
Mikael P. Sundqvist mic...@gmail.com writes:
I can confirm that it is too low in latest standalone. It looks OK at
http://live.contextgarden.net/, though.
I can also add that \surd is way too low in latest standalone (and
only a bit to low in mkiv
Hi Hans,
Thanks for your attention to the issue pointed out by Sanjoy.
On 6 mai 2014, at 20:14, Hans Hagen pra...@wxs.nl wrote:
[…]
all minus' are below the baseline so consider it a feature
Yes this is the case in recent versions of mkiv, but in Plain TeX and mkii this
is not the case:
On 5/6/2014 4:22 PM, Sanjoy Mahajan wrote:
Continuing my recent theme of finding glyphs too low or too high:
The \pm symbol looks like it is set too low, in MkIV.
\setuppagenumbering[location=]
\starttext
$\pm2$
\stoptext
The minus part of the sign lies below the baseline, which looks odd
On 5/6/2014 8:28 PM, Otared Kavian wrote:
Hi Hans,
Thanks for your attention to the issue pointed out by Sanjoy.
On 6 mai 2014, at 20:14, Hans Hagen pra...@wxs.nl
mailto:pra...@wxs.nl wrote:
[…]
all minus' are below the baseline so consider it a feature
Yes this is the case in recent
that's then the virtual lm unicode math (which you can still use in the
latest mkiv if needed)
I still wonder whether the placement is due to the new LM Math font.
yes
-Sanjoy
Mikael P. Sundqvist mic...@gmail.com writes:
I can confirm that it is too low in latest standalone. It looks
the + aligns on the math axis so one can argue if the type-one variant
is ok ... so we would need a smaller (less height) + then which would
look visually weird
Plain TeX doesn't align the plus/minus to the math axis. Rather, the
minus is aligned to the baseline, and the horizontal stroke
\triangle=0234
\mathchardef\bigtriangleup=2234
So \triangle is a math ord and \bigtriangleup a math bin.
For compatibility, that should probably stay true in ConTeXt too---even
the low placement of \bigtriangledown, which I don't understand but
which does reproduce plain TeX's placement.
why
Hans Hagen pra...@wxs.nl writes:
So \triangle is a math ord and \bigtriangleup a math bin.
For compatibility, that should probably stay true in ConTeXt too---even
the low placement of \bigtriangledown, which I don't understand but
which does reproduce plain TeX's placement.
why
So \triangle is a math ord and \bigtriangleup a math bin.
For compatibility, that should probably stay true in ConTeXt too---even
the low placement of \bigtriangledown, which I don't understand but
which does reproduce plain TeX's placement.
Btw, it is still on my agenda to provide a mechanism
On 4/13/2014 4:44 AM, Sanjoy Mahajan wrote:
Otared Kavian ota...@gmail.com writes:
The \triangle operator is used for instance in the « symmetric
difference » of two subsets
Ah, good to learn something about pure mathematics. In my mathematics
degree, my tutor said, You are very good at the
Otared Kavian ota...@gmail.com writes:
The \triangle operator is used for instance in the « symmetric
difference » of two subsets
Ah, good to learn something about pure mathematics. In my mathematics
degree, my tutor said, You are very good at the applied material,
which was not meant as a
Hi,
The \triangle operator is used for instance in the « symmetric difference » of
two subsets: if $E$ is a set and $A \subset E$, and $B \susbet E$, then one
defines
\startformula
A \triangle B := (A \cup B) \setminus (A \cap B).
\stopformula
Then the mapping $(A,B) \mapsto A \triangle B$ is a
I just noticed that the gradient operator (\triangledown) ends up too
low when using Palatino:
\setupbodyfont[palatino]
\starttext
$\triangledown T$
\stoptext
It seems about 3pt too low. Without the \setupbodyfont[palatino], the
placement is fine.
(tested with 2013.05.28 and 2014.03.27 betas
I think you are using the wrong symbol. Or at least I would prefer \nabla as
gradient operator.
Jannik
Am 10.04.2014 um 23:49 schrieb Sanjoy Mahajan san...@mit.edu:
I just noticed that the gradient operator (\triangledown) ends up too
low when using Palatino:
\setupbodyfont[palatino
Jannik,
You are right. \nabla looks much nicer and is placed correctly. (I
still think the \triangledown placement is slightly off.)
My environment files from MkII days have \def\nabla{\triangledown}, so I
never tried the true \nabla until your suggestion.
Thank you.
-Sanjoy
Jannik Voges
On Thu, 10 Apr 2014, Sanjoy Mahajan wrote:
Jannik,
You are right. \nabla looks much nicer and is placed correctly. (I
still think the \triangledown placement is slightly off.)
My environment files from MkII days have \def\nabla{\triangledown}, so I
never tried the true \nabla until your
I cannot say whether the wrong placement is due to the wrong font
metrics or the wrong mapping (mathop vs mathord) by ConTeXt.
I tried '\triangle T' (often used as the Laplacian operator, instead of
writing it out as \nabla^2). That one comes out fine, even though
\triangledown does not. But
On Fri, 11 Apr 2014, Sanjoy Mahajan wrote:
I cannot say whether the wrong placement is due to the wrong font
metrics or the wrong mapping (mathop vs mathord) by ConTeXt.
I tried '\triangle T' (often used as the Laplacian operator, instead of
writing it out as \nabla^2). That one comes out
On Fri, 11 Apr 2014, Aditya Mahajan wrote:
On Fri, 11 Apr 2014, Sanjoy Mahajan wrote:
I cannot say whether the wrong placement is due to the wrong font
metrics or the wrong mapping (mathop vs mathord) by ConTeXt.
I tried '\triangle T' (often used as the Laplacian operator, instead of
Instead of \triangle you should use \Delta for the laplacian (as you
should use \nabla for the gradient).
Mikael
On Fri, Apr 11, 2014 at 6:06 AM, Sanjoy Mahajan san...@mit.edu wrote:
I cannot say whether the wrong placement is due to the wrong font
metrics or the wrong mapping (mathop vs
.
The 2014.02.14 MkIV subscript with the strut looks too low, although the
x^3 with the strut looks reasonable, or is maybe just slightly too high.
The x^\circ looks fine. The x\mathstrut^\circ is too high. But the
20\mathstrut^\circ looks right (and looks too low without the strut).
In 2014.03.27
Hi Sanjoy,
I agree with you to say that the position of subscripts and superscripts in
mkiv is not perfect: the same remark applies to the position of the derivative
sign « prime » as $u’(t)$.
Actually in mkii (and also in plain TeX) the positions of the superscripts in
your example are the
On 3/22/2014 8:17 AM, Otared Kavian wrote:
Hi Sanjoy,
I agree with you to say that the position of subscripts and superscripts in
mkiv is not perfect: the same remark applies to the position of the derivative
sign « prime » as $u’(t)$.
Actually in mkii (and also in plain TeX) the positions
However as Hans pointed out, regarding maths typesetting in mkiv
there are also some font related issues.
we have a more modern implementation in the next beta
I realized that this would also fix my issue with the superscripted
degree symbol coming out too low (which I had mysteriously thought
Dear math typesetting aficianados,
In the following example,
\starttext
$x^3\ x\mathstrut^3$
\stoptext
the superscript without the strut is about 2pt lower than with the
strut, using MkIV. With MkII or plain TeX, they are the same height
(at the higher position obtained by using the \mathstrut
The superscripted degree symbol in $10^\circ$ comes out slightly low.
e.g.
\starttext
\placeformula\startformula
10^\circ \quad 10\mathstrut^\circ
\stopformula
\placeformula\startformula
x^7\quad x\mathstrut^7
\stopformula
\stoptext
I'm not quite sure what's right, but my eye says
I just created a PDF of a bookblock by using MKII to produce the .ps file
and Adobe Acrobat to create the PDF from it. When preflighting the PDF, all
the photos were found to be 300dpi or greater but the table created by the
following code was flagged at being only 150ppi. I don't see this as a
Am 2010-12-23 um 16:11 schrieb Tom:
I just created a PDF of a bookblock by using MKII to produce
the .ps file
and Adobe Acrobat to create the PDF from it.
Why do you make the detour via PS at all?
When preflighting the PDF, all
the photos were found to be 300dpi or greater but the table
Am 2010-12-23 um 16:11 schrieb Tom:
I just created a PDF of a bookblock by using MKII to produce
the .ps file
and Adobe Acrobat to create the PDF from it.
Why do you make the detour via PS at all?
When preflighting the PDF, all
the photos were found to be 300dpi or greater but the
On Thu, Dec 23, 2010 at 4:42 PM, Tom t...@tuxedo-press.com wrote:
Here is an example:
\starttext
\placetable[here,force]{none}
{\starttable[|l|l|l|]
\HL
\VL \bf Player* \VL \bf Position \VL \bf Year Inducted \VL\SR
\HL
\VL Albert Exendine \VL End \VL 1970 \VL\SR
\HL
\VL Joe Guyon \VL
On Thu, Dec 23, 2010 at 8:36 PM, Tom t...@tuxedo-press.com wrote:
On Thu, Dec 23, 2010 at 4:42 PM, Tom t...@tuxedo-press.com wrote:
Here is an example:
\starttext
\placetable[here,force]{none}
{\starttable[|l|l|l|]
\HL
\VL \bf Player* \VL \bf Position \VL \bf Year Inducted \VL\SR
\HL
\VL
On Thu, Dec 23, 2010 at 8:36 PM, Tom t...@tuxedo-press.com wrote:
On Thu, Dec 23, 2010 at 4:42 PM, Tom t...@tuxedo-press.com wrote:
Here is an example:
\starttext
\placetable[here,force]{none}
{\starttable[|l|l|l|]
\HL
\VL \bf Player* \VL \bf Position \VL \bf Year Inducted \VL\SR
\HL
Hello,
I was trying to use a new font (not Computer Modern) in my tex file
and all I get is the font in a very low resolution (see
http://www.nfmh.is/~kari/pub/context/flipp4.pdf). This output was the
result of the following files:
type-garde.tex: http://www.nfmh.is/~kari/pub/context/type
Kári Hreinsson wrote:
The interesting thing is that I can get the fonts with good quality if
I only use TeX. The output of running the file flipp3.tex:
http://www.nfmh.is/~kari/pub/context/flipp3.tex
* with pdftex: http://www.nfmh.is/~kari/pub/context/flipp3.pdf
* with texexec --pdf:
Thanks, this worked.
I added the appropriate lines to 8r-base.map found in the local texmf
root. That should be clean enough? :)
Thanks again,
Kári Hreinsson
On 11/7/05, Taco Hoekwater [EMAIL PROTECTED] wrote:
Kári Hreinsson wrote:
The interesting thing is that I can get the fonts with good
hi all.
what's your best way of getting the current font name, regardless of how
it's set (e.g., typescript, unicode, definedfont, low-level \font
definitions...)?
I certainly know about \truefontname{}, but what to put in the braces
Adam Lindsay wrote:
hi all.
what's your best way of getting the current font name, regardless of how
it's set (e.g., typescript, unicode, definedfont, low-level \font
definitions...)?
I certainly know about \truefontname{}, but what to put in the braces?
tex: \fontname\font
also in context
Hans Hagen said this at Thu, 25 Nov 2004 13:11:49 +0100:
tex: \fontname\font
Thanks Hans. That's reliable.
also in context: \purefontname\font
This fails with the XeTeX quoted-with-spaces fonts (just gives Chaparral
) . I wasn't looking to test that sort of thing, but there you go.
Clearly
Adam Lindsay wrote:
Clearly \def\splitoffpurefontname#1 #2\\{#1} isn't enough. :/
if this fails ...
\unprotected
\def\purefontname#1%
[EMAIL PROTECTED]@[EMAIL PROTECTED] \\}
... then you're stuck for a few days (tomorrow i'm away)
Hans
On Tue, 31 Aug 2004 11:49:59 +0200, Hans wrote:
With every change you make, there's almost always a complaint. :) Here's mine:
In English (American British), criterium is more correctly
criterion. Similarly, palet is palette. I have notes on other
little complaints, but these are the big
On Tue, 31 Aug 2004 11:50:20 +0200, Hans wrote:
btw, i uploaded a new alpha
You re-uploaded the old alpha, actually. :-)
--
groeten,
Taco
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Wednesday, September 1, 2004 Taco Hoekwater wrote:
On Tue, 31 Aug 2004 11:49:59 +0200, Hans wrote:
With every change you make, there's almost always a complaint. :) Here's mine:
In English (American British), criterium is more correctly
criterion. Similarly, palet is palette. I have notes
Le 1 sept. 04, à 14:24, Giuseppe Bilotta a écrit :
align=flushleft % maps to 'old' right
align=flushright % maps to 'old' left
+1 to this proposal. This way we can then later map right and
left to the *correct* ones :)
+1 for me, it's more natural!
-- Maurice Diamantini
Taco Hoekwater wrote:
On Tue, 31 Aug 2004 11:49:59 +0200, Hans wrote:
With every change you make, there's almost always a complaint. :) Here's mine:
In English (American British), criterium is more correctly
criterion. Similarly, palet is palette. I have notes on other
little complaints, but
Adam Lindsay wrote:
I uploaded the upcoming release,
http://www.pragma-ade.com/context/alpha This version is low level
english (commands, keywords, values). It is
Very cool. I can't imagine how huge a job this was.
While looking through mult-com and -con, I noticed a few capitalised
btw, i uploaded a new alpha
Han s
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
Hi,
I uploaded the upcoming release,
http://www.pragma-ade.com/context/alpha
This version is low level english (commands, keywords, values). It is possible that some functionality is not working, but as far as i can see most should work as expected. If you find low level dutch in the source
56 matches
Mail list logo
